The purpose of many software that we write is to retrieve data from a data store and display it for the user. Again after the user changes the data, the system stores the updates in the data store.
In simple words the key flow of information is between the data store and the user interface, isn’t it?
MVC which stands for Model View and Controller is actually a software architecture design pattern.
Model-View-Controller is a fundamental design pattern for the separation of user interface logic from business logic. The MVC pattern hinges on a clean separation of objects into one of three categories - models for maintaining data, views for displaying all or a portion of the data, and controllers for handling events that affect the model or view.
Controllers are responsible for taking inputs from the view then convert it into appropriate format so that model can understand it. Then it instructs the model to perform actions based on that input.Then again it takes the result back from the model (if any) and forwards the response to View.
It is important to note that both the view and the controller depend on the model. However, the model depends on neither the view nor the controller. This is one the key benefits of the separation. This separation allows the model to be built and tested independent of the visual presentation.
In simple words the key flow of information is between the data store and the user interface, isn’t it?
MVC which stands for Model View and Controller is actually a software architecture design pattern.
Model-View-Controller is a fundamental design pattern for the separation of user interface logic from business logic. The MVC pattern hinges on a clean separation of objects into one of three categories - models for maintaining data, views for displaying all or a portion of the data, and controllers for handling events that affect the model or view.
Controllers are responsible for taking inputs from the view then convert it into appropriate format so that model can understand it. Then it instructs the model to perform actions based on that input.Then again it takes the result back from the model (if any) and forwards the response to View.
It is important to note that both the view and the controller depend on the model. However, the model depends on neither the view nor the controller. This is one the key benefits of the separation. This separation allows the model to be built and tested independent of the visual presentation.